﻿<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
	<link rel="Stylesheet" type="text/css" media="screen" href="Screen.css" />
  <title>STP_StartBridge</title>
</head>
<body>
	<h3>STP_StartBridge</h3>
	<hr />
<pre>
void STP_StartBridge
(
    STP_BRIDGE*   bridge,
    unsigned int  timestamp
);
</pre>
	<h4>
		Summary</h4>
	<p>Starts the Spanning Tree Protocol on a bridge.
		</p>
	<h4>
		Parameters</h4>
	<dl>
		<dt>bridge</dt>
		<dd>Pointer to a STP_BRIDGE object, obtained from <a href="STP_CreateBridge.html">
			STP_CreateBridge</a>.</dd>
		<dt>timestamp</dt>
		<dd>A timestamp used for the debug log. </dd>
	</dl>
	<h4>
		Remarks</h4>
	<p>
		Starting the Spanning Tree Protocol from application code is usually a 
		three-step procedure:</p>
	<ul>
		<li>a call to <a href="STP_CreateBridge.html">STP_CreateBridge</a>, which allocates 
			internal structures and initializes all parameters to default values;</li>
		<li>various calls to functions such as <a href="STP_SetBridgePriority.html">STP_SetBridgePriority</a>
		and <a href="STP_SetStpVersion.html">STP_SetStpVersion</a>, possibly with values 
			read from a configuration file; the protocol is not yet started, so there won&#39;t 
			be any STP activity with temporary parameters.</li>
		<li>a call to this function, which starts the protocol directly with 
			application-specified parameters.</li>
	</ul>
	<p>
		The 
		application must not call this function for already-started bridges.</p>

	<p>
			Execution of this function is a potentially lengthy process. 
			It may call various callbacks multiple times.</p>
	<p>
			This function may not be called from within an <a href="STP_CALLBACKS.html">STP callback</a>.</p>

</body>
</html>
